Purchasing Options

Field/Flag	Description
PO Price Type	Pick list used to set the default selection for the field of the same name on the Item Master General 1 tab to be used when a new Part is added. Determines which Item Master field will be used to set the price when the item is added to a Purchase Order line.
Pricing Order Date	Pick list used to define which date on the Dates tab of the Edit Purchase Order Line form will be used to determine if a Purchase Order falls within the range of any applicable Pricing Orders. Options are: Order Date PO Date 1-5 Example: Assume this field is set to "Order Date" and a Pricing Order exists with a "Release" date of Aug 1st and an "Expires" date of Aug 31st. Creating a new Purchase Order with a Vendor and quantities matching the Pricing Order and a "Order Date" date of July 15th will not utilize the Pricing Order details. However, if the "Order Date" date is changed to Aug 18th, the Pricing Order details will be utilized. If multiple pricing orders exists for items entered of Purchase Orders, reference the "Pricing Order Sort" field below for details on how pricing orders will be applied.
Pricing Order Sort	Pick list used to define how pricing orders will be selected when multiple pricing orders are in effect for items entered on Purchase Orders. Options are Lowest Price - system automatically selects the pricing order with the lowest price based on the item number being placed on the PO. This is the default option. First Effective - system automatically selects the pricing order with the earliest effective date (based on the Pricing Order Date field above). Example: The following pricing orders exist: Item A from 1/1/2019 - 12/31/2021 for $6.00/case Item A from 1/1/2020 - 12/31/2021 for $7.00/case Item A from 1/1/2020 - 1/31/2020 for $5.50/case Item A from 4/1/2020 - 4/30/2020 for $7.50/case Pricing Order Sort set to "First Effective" Pricing Order Sort set to "Lowest Price" PO entered with an order date of 12/20/2019 results in a price of $6.00 PO entered with an order date of 12/20/2019 results in a price of $6.00 PO entered with an order date of 1/15/2020 results in a price of $7.00 PO entered with an order date of 1/15/2020 results in a price of $5.50 PO entered with an order date of 2/14/2020 results in a price of $7.00 PO entered with an order date of 2/14/2020 results in a price of $6.00 PO entered with an order date of 4/1/2020 results in a price of $7.00 PO entered with an order date of 4/1/2020 results in a price of $6.00 PO entered with an order date of 5/5/2020 results in a price of $7.00 PO entered with an order date of 5/5/2020 results in a price of $6.00j If the "Prompt PO Blanket Orders" flag is checked, and a value is specified in the "Blanket Quantity" field on the pricing order, the logic in this field will not be applied. If the "Prompt PO Blanket Order" flag is unchecked, the logic in this field is always applied.
Default Order Type	Pick list used to determine if new Purchase Orders begin as Requisitions or Purchase Orders.
MRP Order Type	Pick list used to determine if new Purchase Orders begin as Requisitions or Purchase Orders when created via the "Create PO" or "Auto PO" buttons in MRP. Having POs default to Requisitions is useful in situations where Work Flows exist to control when/how POs are created and approved.
Drop Shipment Order Type	Pick list used to determine how the "Order Type" field will be set when Drop Shipment Purchase Order are created in the system. Options are: Purchase Order (Default) Requisition This field supports Work Flow functionality for Drop Shipments. The functionally in this field introduces two new changes: Work Flows are now attached to the Drop Shipment Purchase Order by using the Default Work Flow set on the Vendor record. If the Purchase Order option is set in this field the system will check if any of the sequences on the attached work flow are required to make PO. If there are no work flow sequences set to required to make PO, the system will create the order as a purchase order type. If any sequence(s) is required to make PO, the system will create the order as a requisition order type even if this field is set to "Purchase Order".
Link PO's To	Determines how the system will link purchase orders when using the "Link POs" button on the purchase order entry screen. Options are: PO Header - if selected, the system will allow users to link the individual purchase order being modified to multiple purchase orders via the Link POs filter and mover forms that are displayed when using the "Link POs" button. PO Links - if selected, the system will allow users to link orders from the one being modified to multiple orders, just as in the PO Header option above, but also allow linking to occur in the other direction. meaning multiple purchase orders can be linked back to any purchase order and not just the order being viewed or modified. This is accomplished by storing links in the Linked Orders (dtpurlink) table. Added in version 17.04.003.0000
Last Cost Entries	Defines how many of the most recent "Last Cost" entries should be averaged when calculating the weighted average of the actual purchase or production cost of a Part. The "Last Cost" value is stored on the Item Master Costs 2 tab. Can be used to average out the effect of spot or emergency buys. Example: Item A generally costs $1.00 each when purchased. In an emergency situation, sufficient amounts of this item are purchased locally for $8.00 each. If the value in this field is set to "1", then the Last Cost field on the Item Master record will not reflect a realistic average. If, however, this field is set to "3" or "4", the Last Cost field will represent a more realistic inventory cost for this item. Note: The calculation evaluates the costs on the lines/items on Purchase Orders and/or production Jobs in the system and not the costs of the Lots in inventory. This is done to ensure that the "Last Cost" is calculated correctly depending on the inventory costing method. Negative quantity purchase orders are not considered in last cost calculations.
Max PO Adjust	Defines the maximum amount, in dollars, that an invoice is allowed to differ from the Purchase Order amount when entering an amount in the "Adjustment" field on the Invoice form. The difference is posted to the "AP Adjustments" account indicated on the System > Options > Accounts tab. The freight amount can exceed this quantity but the adjustment amount cannot. This field does not control the maximum amount when making adjustments in other parts of the system.
Max PO Dollars 1-3	Defines the three maximum dollar levels for Purchase Orders. User Groups or specific Users may be configured to be allowed to exceed this level. Useful because they allow companies to establish hard limits without the need to require approvals for amounts up to and including those set in these fields. If the Total Amount Due is later changed on the Purchase Order, these values will be checked again.
PO QC Text	Memo field used to specify the QC information to be displayed on purchasing forms. The available fields for use in this text are: ql_fiid, dmqc2., q3_name, q3_method, and dtqc4..
Lot # Expression	Memo field used to store an expression used to create User Lot numbers during PO receipt. When freight3 loads up, if there is an expression defined, Lot number will be calculated and displayed in the grid. If not, proceed as before. In freight4 and Receive PO in WMS, when the Attrib1, Attrib2, Attrib3, Vendor date, or Expire date fields change, if a Lot # Expression exists, the expression will re-fire. Added F_LOTVAL(field to receive, key field, where field) to expression processor. Field to receive is the fi_ field users want returned (always returned as a string). Key field is the fi_field users want to match the where field to. The text "Lot Required" will be overwritten by the results of the defined Lot # Expression. When using the F_LOTVAL function, users can include a filter to query the "dtfifo" table. Using the F_LOTVAL function, 2 parameters can be passed; The first one is the one to filter on (like it was before) and the second now expects a sql where clause, "fi_prid = m.pu_prid AND fi_attrib1 = m.fi_attrib1". Example: IIF (EMPTY (CHILDLOT ()), IIF (EMPTY (attrib1), "Enter Vendor Lot #", IIF (EMPTY (F_LOTVAL ("fi_userlot", "fi_attrib1 = m.attrib1 AND fi_prid = m.pu_prid")), ALLT (STR (MOD (IIF (GETVAR ("CountNum") = 0, SETVAR ("CountNum", INCREMENT ("LOT")), GETVAR ("CountNum")),99999),6,0)), F_LOTVAL ("fi_userlot", "fi_attrib1", attrib1))), CHILDLOT ()) The following are available to this field: PO Header data. Example: TRANS(tp_purnum, "99999999999"). PO Line data for the line that the lot is being received against. Part number information, or blank part number info if it is an expense line (prid = 0). The attributes that the user has filled in. The expiration date. The vendor lot date.
PO Price Factor Script	Memo field used to enter a custom price factor for Purchasing Orders. Before the inventory is received for the Purchase Order, if this field is populated, the script will fire for each line item. Only fields from the Purchase Order Lines table (dtpur) are available for use in this script. Examples: Confirmation Date (pu_confirm), Freight Cost (pu_frtcost), etc. When returning a decimal value, any line items that do not require a factor will return "0" for that line.
Default Receiving Qty	Pick list used to set the default quantity per line that will be received via the Receive function. Full - Sets the "Receive" quantity to match the full "Ordered" quantity. Zero - Sets the "Receive" quantity to zero and the "Backorder" quantity to match the full "Ordered" quantity. Useful in situations where customers want to ensure that receivers verify what is being received line by line instead of simply clicking the "Receive" button for the entire Purchase Order or for scenarios where something like 50 lines are typically added to a Purchase Order and only one or two lines are received per shipment.
Over Receipt % Limit	Defines the default value for the field of the same name on the Item Master General 2 tab to be used when a new Part is added. Represents the percent of the original order amount that may be received in addition to the original order amount. The limit is only applied if the "Enforce Over Receipt % Limit" box is checked. Security exists to allow power users to exceed this limit.
Enforce Over Receipt % Limit	If checked, the flag of the same name on the Item Master General 2 tab will be checked by default when a new Part is added. If checked on an Item Master, the system will enforce the "Over Receipt % Limit" defined.
PO Date 1-5 Calc.	Memo fields used to define calculations for the default values for the PO Date 1-5 fields. Captions for the PO Date 1-5 fields are managed via the System > Options > Purchasing tab. Calculations can reference the current date as DATE() or other Purchase Order dates by their field name.
PO Expires Calc.	Memo field used to define the calculation for the default value of the "Expires" date on the Purchase Order header Dates tab. The "Expires" date may be used to determine the expiration date for Pricing Orders, but this is optional.
Freight In Part	Sets the Part that is added to Purchase Orders when Freight is added to purchase orders, including when creating purchase orders to account for freight charges after receipt of the initial purchase order for goods or services. The search box for this field filters for Item Masters marked as Purchasable. Available beginning in version 16.05.
PO Remember Last Part	If checked, the system will remember the last Part ordered and use it as the default when adding a new line to a Purchase Order.
Accept Backorders	If checked, the flag of the same name on the General tab of the Edit Vendor form will be checked by default when a new Vendor is added. Indicates that if a Purchase Order is only partially received, the remaining quantity will be added to a backorder.
Cancel Backorders When Un-Receiving	If checked, un-received backorders will be cancelled for a Purchase Order that is un-received. Pre-paid backorders will not be cancelled with this flag checked. If there are both received and un-received backorders, only the un-received ones will be cancelled.
Auto Invoice	If checked, the flag of the same name on the General tab of the Edit Vendor form will be checked by default when a new Vendor is added. Indicates that Purchase Orders for the Vendor will be automatically invoiced upon material receipt.
Auto Receive Linked Freight PO	If checked, and a freight purchase order is linked to another purchase order, and that purchase order is received, the system will automatically receive the Freight PO on the same date. Freight purchase orders are created via the "Freight PO" button on certain purchase order reports, and when accessing purchase orders and sales orders in view only mode. This field is unchecked by default. Added in version 17.01.016.
Discount Freight	If checked, the "Take Discounts On Freight" flag on the General tab of the Edit Vendor form will be checked by default when a new Vendor is added. Indicates that any Terms discount applied to the order also applies to freight on the order.
Print Document Group After Receipt	If checked, sets the "Print Document Group After Receipt" field on the Receive Purchase Orders form, allowing the Document Group selected on the Purchase Order to be printed after receipt. The default value for the Document Group for the Purchase Order will be populated, if present, from the Document Group on the Vendor record. This applies when a new PO is created in any way, either manually, via MRP, or via MRO. Added in version 17.04.003.
Print Forms After Receipt	If checked, the "Print PO Labels After Receipt" flag on the Receive form will be checked by default. Indicates the Part labels for the material received are printed immediately after the Purchase Order has been marked as received.
Prompt PO Blanket Orders	If checked, when a Part that belongs on an existing Pricing PO is added to a Purchase Order, the system prompts the user to select a Pricing Order to use. This also applies when entering a purchasing requisition by selecting an Order Type of "Requisition" on the Order Entry form. Useful in situations where multiple open blanket orders exist for the same Vendor/item and users want to select based on additional criteria besides the lowest price. In MRP, the system will display the MRP Blanket PO form when this field is checked and when using the "Create PO" or "Auto PO" buttons for any part and vendor combination that applies to an open blanket order. In time-phased MRP, the form displays one row for each part and due to dock date combination. In instant MRP, the system displays one row for each part combined to one date. Notes If the user clicks the "Continue" button and a blanket PO was not chosen, the system will create the appropriate purchase order lines without the blanket pricing order applied. If this field is not checked, pricing orders and blanket quantities will still be applied automatically and users will not be prompted to select an open pricing order. When using instant MRP and the Auto PO option, the due to dock date will be empty for any created purchase orders. In this case, today's date will be used to decide which blanket orders are valid.
Use Line Dates On Pricing Orders	If checked, when determining the effective pricing order dates in the system on a Purchase Order, uses the line level date to determine the starting date of the pricing order line. This then also uses the Expires date to determine the ending date of the pricing order line. Useful in situations where price changes are known for future dates to ensure the Purchase Order aligns with the current prices instead of future ones. When not checked, simply looks at the order header date to determine the corresponding starting and ending dates.
Re-Calc PO Prices On Receipt	If checked, the system will reevaluate all valid pricing orders and, if applicable, will apply any pricing changes for items on purchase orders after purchase order receipt. This field is unchecked by default. Business Case: This option is useful in situations where pricing orders are modified frequently and Purchase Orders have already been entered in Deacom. Vendors may price items based on a different purchase order date, such as ordered date, pick up date, or received date. If this box is checked, then modification to Pricing Orders can still be applied after applicable purchase orders have been entered but before items/lots are received into inventory. When operating in FIFO cost mode, the lots received will reflect updated prices.
Display All PO Lines For Adjustments During Invoicing	If checked, one row for each Purchase Order line will automatically be displayed on the Order Adjustments form when performing adjustments during PO invoicing. Also, the following changes will be enabled when editing the adjustment lines on the form: The "Amount" and "Extension" fields will be disabled. These fields will display the item price and total line extension from the PO line. The "Invoice Amount" will now be available for entry/updating. The "Invoiced Extension" fields will display the appropriate extension information. A line item indicating the order adjustment will only be added to the PO if there is a difference between the received amount and invoiced amount. In addition, the existing PO line will be updated with the users inputted value in the "Invoice Amount" field. Note: This field was added to allow increased functionality for matching the data between received and invoiced amounts and making adjustments as necessary. If this field is left unchecked, the current order adjustment functionality will be in effect.

PO Price Type

Pick list used to set the default selection for the field of the same name on the Item Master General 1 tab to be used when a new Part is added.

Determines which Item Master field will be used to set the price when the item is added to a Purchase Order line.

Pricing Order Date

Pick list used to define which date on the Dates tab of the Edit Purchase Order Line form will be used to determine if a Purchase Order falls within the range of any applicable Pricing Orders. Options are:

Order Date
PO Date 1-5
Example: Assume this field is set to "Order Date" and a Pricing Order exists with a "Release" date of Aug 1st and an "Expires" date of Aug 31st. Creating a new Purchase Order with a Vendor and quantities matching the Pricing Order and a "Order Date" date of July 15th will not utilize the Pricing Order details. However, if the "Order Date" date is changed to Aug 18th, the Pricing Order details will be utilized.
If multiple pricing orders exists for items entered of Purchase Orders, reference the "Pricing Order Sort" field below for details on how pricing orders will be applied.

Pricing Order Sort

Pick list used to define how pricing orders will be selected when multiple pricing orders are in effect for items entered on Purchase Orders. Options are

Lowest Price - system automatically selects the pricing order with the lowest price based on the item number being placed on the PO. This is the default option.
First Effective - system automatically selects the pricing order with the earliest effective date (based on the Pricing Order Date field above).
Example: The following pricing orders exist:
- Item A from 1/1/2019 - 12/31/2021 for $6.00/case
- Item A from 1/1/2020 - 12/31/2021 for $7.00/case
- Item A from 1/1/2020 - 1/31/2020 for $5.50/case
- Item A from 4/1/2020 - 4/30/2020 for $7.50/case

Pricing Order Sort set to "First Effective"

Pricing Order Sort set to "Lowest Price"

PO entered with an order date of 12/20/2019 results in a price of $6.00
PO entered with an order date of 12/20/2019 results in a price of $6.00
PO entered with an order date of 1/15/2020 results in a price of $7.00
PO entered with an order date of 1/15/2020 results in a price of $5.50
PO entered with an order date of 2/14/2020 results in a price of $7.00
PO entered with an order date of 2/14/2020 results in a price of $6.00
PO entered with an order date of 4/1/2020 results in a price of $7.00
PO entered with an order date of 4/1/2020 results in a price of $6.00
PO entered with an order date of 5/5/2020 results in a price of $7.00
PO entered with an order date of 5/5/2020 results in a price of $6.00j
If the "Prompt PO Blanket Orders" flag is checked, and a value is specified in the "Blanket Quantity" field on the pricing order, the logic in this field will not be applied. If the "Prompt PO Blanket Order" flag is unchecked, the logic in this field is always applied.

Default Order Type

Pick list used to determine if new Purchase Orders begin as Requisitions or Purchase Orders.

MRP Order Type

Pick list used to determine if new Purchase Orders begin as Requisitions or Purchase Orders when created via the "Create PO" or "Auto PO" buttons in MRP.

Having POs default to Requisitions is useful in situations where Work Flows exist to control when/how POs are created and approved.

Drop Shipment Order Type

Pick list used to determine how the "Order Type" field will be set when Drop Shipment Purchase Order are created in the system. Options are:

Purchase Order (Default)
Requisition

This field supports Work Flow functionality for Drop Shipments. The functionally in this field introduces two new changes:

Work Flows are now attached to the Drop Shipment Purchase Order by using the Default Work Flow set on the Vendor record.
If the Purchase Order option is set in this field the system will check if any of the sequences on the attached work flow are required to make PO. If there are no work flow sequences set to required to make PO, the system will create the order as a purchase order type. If any sequence(s) is required to make PO, the system will create the order as a requisition order type even if this field is set to "Purchase Order".

Link PO's To

Determines how the system will link purchase orders when using the "Link POs" button on the purchase order entry screen. Options are:

PO Header - if selected, the system will allow users to link the individual purchase order being modified to multiple purchase orders via the Link POs filter and mover forms that are displayed when using the "Link POs" button.
PO Links - if selected, the system will allow users to link orders from the one being modified to multiple orders, just as in the PO Header option above, but also allow linking to occur in the other direction. meaning multiple purchase orders can be linked back to any purchase order and not just the order being viewed or modified. This is accomplished by storing links in the Linked Orders (dtpurlink) table.
Added in version 17.04.003.0000

Last Cost Entries

Defines how many of the most recent "Last Cost" entries should be averaged when calculating the weighted average of the actual purchase or production cost of a Part.

The "Last Cost" value is stored on the Item Master Costs 2 tab.
Can be used to average out the effect of spot or emergency buys.
Example: Item A generally costs $1.00 each when purchased. In an emergency situation, sufficient amounts of this item are purchased locally for $8.00 each. If the value in this field is set to "1", then the Last Cost field on the Item Master record will not reflect a realistic average. If, however, this field is set to "3" or "4", the Last Cost field will represent a more realistic inventory cost for this item.
Note: The calculation evaluates the costs on the lines/items on Purchase Orders and/or production Jobs in the system and not the costs of the Lots in inventory. This is done to ensure that the "Last Cost" is calculated correctly depending on the inventory costing method.
Negative quantity purchase orders are not considered in last cost calculations.

Max PO Adjust

Defines the maximum amount, in dollars, that an invoice is allowed to differ from the Purchase Order amount when entering an amount in the "Adjustment" field on the Invoice form.

The difference is posted to the "AP Adjustments" account indicated on the System > Options > Accounts tab.
The freight amount can exceed this quantity but the adjustment amount cannot.
This field does not control the maximum amount when making adjustments in other parts of the system.

Max PO Dollars 1-3

Defines the three maximum dollar levels for Purchase Orders.

User Groups or specific Users may be configured to be allowed to exceed this level.
Useful because they allow companies to establish hard limits without the need to require approvals for amounts up to and including those set in these fields.
If the Total Amount Due is later changed on the Purchase Order, these values will be checked again.

PO QC Text

Memo field used to specify the QC information to be displayed on purchasing forms.

The available fields for use in this text are: ql_fiid, dmqc2.*, q3_name, q3_method, and dtqc4.*.

Lot # Expression

Memo field used to store an expression used to create User Lot numbers during PO receipt.

When freight3 loads up, if there is an expression defined, Lot number will be calculated and displayed in the grid. If not, proceed as before.
In freight4 and Receive PO in WMS, when the Attrib1, Attrib2, Attrib3, Vendor date, or Expire date fields change, if a Lot # Expression exists, the expression will re-fire.
Added F_LOTVAL(field to receive, key field, where field) to expression processor.
- Field to receive is the fi_ field users want returned (always returned as a string).
- Key field is the fi_field users want to match the where field to.
The text "Lot Required" will be overwritten by the results of the defined Lot # Expression.
When using the F_LOTVAL function, users can include a filter to query the "dtfifo" table. Using the F_LOTVAL function, 2 parameters can be passed; The first one is the one to filter on (like it was before) and the second now expects a sql where clause, "fi_prid = m.pu_prid AND fi_attrib1 = m.fi_attrib1".
Example: IIF (EMPTY (CHILDLOT ()), IIF (EMPTY (attrib1), "Enter Vendor Lot #", IIF (EMPTY (F_LOTVAL ("fi_userlot", "fi_attrib1 = m.attrib1 AND fi_prid = m.pu_prid")), ALLT (STR (MOD (IIF (GETVAR ("CountNum") = 0, SETVAR ("CountNum", INCREMENT ("LOT")), GETVAR ("CountNum")),99999),6,0)), F_LOTVAL ("fi_userlot", "fi_attrib1", attrib1))), CHILDLOT ())
The following are available to this field:
- PO Header data. Example: TRANS(tp_purnum, "99999999999").
- PO Line data for the line that the lot is being received against.
- Part number information, or blank part number info if it is an expense line (prid = 0).
- The attributes that the user has filled in.
- The expiration date.
- The vendor lot date.

PO Price Factor Script

Memo field used to enter a custom price factor for Purchasing Orders. Before the inventory is received for the Purchase Order, if this field is populated, the script will fire for each line item.

Only fields from the Purchase Order Lines table (dtpur) are available for use in this script. Examples: Confirmation Date (pu_confirm), Freight Cost (pu_frtcost), etc.
When returning a decimal value, any line items that do not require a factor will return "0" for that line.

Default Receiving Qty

Pick list used to set the default quantity per line that will be received via the Receive function.

Full - Sets the "Receive" quantity to match the full "Ordered" quantity.
Zero - Sets the "Receive" quantity to zero and the "Backorder" quantity to match the full "Ordered" quantity.
- Useful in situations where customers want to ensure that receivers verify what is being received line by line instead of simply clicking the "Receive" button for the entire Purchase Order or for scenarios where something like 50 lines are typically added to a Purchase Order and only one or two lines are received per shipment.

Over Receipt % Limit

Defines the default value for the field of the same name on the Item Master General 2 tab to be used when a new Part is added.

Represents the percent of the original order amount that may be received in addition to the original order amount.
The limit is only applied if the "Enforce Over Receipt % Limit" box is checked. Security exists to allow power users to exceed this limit.

Enforce Over Receipt % Limit

If checked, the flag of the same name on the Item Master General 2 tab will be checked by default when a new Part is added.

If checked on an Item Master, the system will enforce the "Over Receipt % Limit" defined.

PO Date 1-5 Calc.

Memo fields used to define calculations for the default values for the PO Date 1-5 fields.

Captions for the PO Date 1-5 fields are managed via the System > Options > Purchasing tab.
Calculations can reference the current date as DATE() or other Purchase Order dates by their field name.

PO Expires Calc.

Memo field used to define the calculation for the default value of the "Expires" date on the Purchase Order header Dates tab.

The "Expires" date may be used to determine the expiration date for Pricing Orders, but this is optional.

Freight In Part

Sets the Part that is added to Purchase Orders when Freight is added to purchase orders, including when creating purchase orders to account for freight charges after receipt of the initial purchase order for goods or services.

The search box for this field filters for Item Masters marked as Purchasable.
Available beginning in version 16.05.

PO Remember Last Part

If checked, the system will remember the last Part ordered and use it as the default when adding a new line to a Purchase Order.

Accept Backorders

If checked, the flag of the same name on the General tab of the Edit Vendor form will be checked by default when a new Vendor is added.

Indicates that if a Purchase Order is only partially received, the remaining quantity will be added to a backorder.

Cancel Backorders When Un-Receiving

If checked, un-received backorders will be cancelled for a Purchase Order that is un-received.

Pre-paid backorders will not be cancelled with this flag checked.
If there are both received and un-received backorders, only the un-received ones will be cancelled.

Auto Invoice

If checked, the flag of the same name on the General tab of the Edit Vendor form will be checked by default when a new Vendor is added.

Indicates that Purchase Orders for the Vendor will be automatically invoiced upon material receipt.

Auto Receive Linked Freight PO

If checked, and a freight purchase order is linked to another purchase order, and that purchase order is received, the system will

automatically receive the Freight PO on the same date.

Freight purchase orders are created via the "Freight PO" button on certain purchase order reports, and when accessing purchase orders and sales orders in view only mode.
This field is unchecked by default. Added in version 17.01.016.

Discount Freight

If checked, the "Take Discounts On Freight" flag on the General tab of the Edit Vendor form will be checked by default when a new Vendor is added.

Indicates that any Terms discount applied to the order also applies to freight on the order.

Print Document Group After Receipt

If checked, sets the "Print Document Group After Receipt" field on the Receive Purchase Orders form, allowing the Document Group selected on the Purchase Order to be printed after receipt.

The default value for the Document Group for the Purchase Order will be populated, if present, from the Document Group on the Vendor record. This applies when a new PO is created in any way, either manually, via MRP, or via MRO.
Added in version 17.04.003.

Print Forms After Receipt

If checked, the "Print PO Labels After Receipt" flag on the Receive form will be checked by default.

Indicates the Part labels for the material received are printed immediately after the Purchase Order has been marked as received.

Prompt PO Blanket Orders

If checked, when a Part that belongs on an existing Pricing PO is added to a Purchase Order, the system prompts the user to select a Pricing Order to use. This also applies when entering a purchasing requisition by selecting an Order Type of "Requisition" on the Order Entry form.

Useful in situations where multiple open blanket orders exist for the same Vendor/item and users want to select based on additional criteria besides the lowest price.
In MRP, the system will display the MRP Blanket PO form when this field is checked and when using the "Create PO" or "Auto PO" buttons for any part and vendor combination that applies to an open blanket order. In time-phased MRP, the form displays one row for each part and due to dock date combination. In instant MRP, the system displays one row for each part combined to one date.

Notes

If the user clicks the "Continue" button and a blanket PO was not chosen, the system will create the appropriate purchase order lines without the blanket pricing order applied.
If this field is not checked, pricing orders and blanket quantities will still be applied automatically and users will not be prompted to select an open pricing order.
When using instant MRP and the Auto PO option, the due to dock date will be empty for any created purchase orders. In this case, today's date will be used to decide which blanket orders are valid.

Use Line Dates On Pricing Orders

If checked, when determining the effective pricing order dates in the system on a Purchase Order, uses the line level date to determine the starting date of the pricing order line. This then also uses the Expires date to determine the ending date of the pricing order line.

Useful in situations where price changes are known for future dates to ensure the Purchase Order aligns with the current prices instead of future ones.

When not checked, simply looks at the order header date to determine the corresponding starting and ending dates.

Re-Calc PO Prices On Receipt

If checked, the system will reevaluate all valid pricing orders and, if applicable, will apply any pricing changes for items on purchase orders after purchase order receipt.

This field is unchecked by default.
Business Case: This option is useful in situations where pricing orders are modified frequently and Purchase Orders have already been entered in Deacom. Vendors may price items based on a different purchase order date, such as ordered date, pick up date, or received date. If this box is checked, then modification to Pricing Orders can still be applied after applicable purchase orders have been entered but before items/lots are received into inventory. When operating in FIFO cost mode, the lots received will reflect updated prices.

Display All PO Lines For Adjustments During Invoicing

If checked, one row for each Purchase Order line will automatically be displayed on the Order Adjustments form when performing adjustments during PO invoicing. Also, the following changes will be enabled when editing the adjustment lines on the form:

The "Amount" and "Extension" fields will be disabled. These fields will display the item price and total line extension from the PO line.
The "Invoice Amount" will now be available for entry/updating.
The "Invoiced Extension" fields will display the appropriate extension information.
A line item indicating the order adjustment will only be added to the PO if there is a difference between the received amount and invoiced amount. In addition, the existing PO line will be updated with the users inputted value in the "Invoice Amount" field.

Note: This field was added to allow increased functionality for matching the data between received and invoiced amounts and making adjustments as necessary. If this field is left unchecked, the current order adjustment functionality will be in effect.